Contracts                                                                                           

The Contract Management product in the GEP QUANTUM suite brings together procurement, legal, sales and other stakeholders across the contract life cycle in one intuitive, easy-to-deploy contract administration, management and compliance solution. It allows you to author, collaborate, and aggregate contracts in a central repository for effective contract compliance, administration, and utilization.

In this release, 07 features/enhancements have been added to Contracts.

Ability to Delete Contracts via Bulk Upload

PRJCT-10364 | Configurable: Yes

With this release, the Bulk Upload utility now supports Contract deletion via bulk utility template with mandatory fields Operation, Contract Number, and Revision Number. You can delete Contracts for eligible statuses along with all associated data, linkages, and notifications.

Configuration Details:

  • Setting Name: CLM_BulkdeleteValidStatusList

  • Possible Values: All Statuses

  • Default Values:

  • Draft

  • Author Contract

  • Rejected

  • Withdrawn

  • Terminated

  • Cancelled

  • Executed

  • Live

  • Expired

Enhanced Validations in Bulk Attachment Upload

PRJCT-10557 | Configurable: No

With this release, the Bulk Attachment Upload process includes enhanced validations.  Rows with invalid Classification Type, Contract Number, or File Name are now rejected with enhanced error messages.

Improved Clause Comparison in GEP Doc Plus

PRJCT-10188 | Configurable: No

With this release, the Compare Versions pop-up in GEP Doc Plus provides enhanced visibility into clause recommendations. You can now clearly distinguish between AI-recommended clauses and library clauses through labelled tags. Clause differences are highlighted word-by-word, with accurate handling of negations and minor edits. A static legend supports insertions (green highlight ) and deletions (red strikethrough). Additionally, you can toggle Highlights Difference on or off without impacting the layout.

Display Approval Summary Date & Time Based on User's Locale

PRJCT-10373 | Configurable: Yes

With this release, the approval summary values in Contract Metadata Export display date and time-based on the configured offset settings. This reduces ambiguity across global teams by providing consistent date/time representation and time zone details.

Configuration Details:

  • Setting Name: Configure Contract Notification Date & Time Based on Recipient’s Locale

  • Feature Group: CLM.Notification

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

Configuration Details:

  • Setting Name: Configure Contract Date & Time Based on Offset Setting

  • Feature Group: CLM.Notification

  • Possible Values:

  • datewithoffset

  • datewithoutoffset

  • datetimewithoffset

  • datetimewithoutoffset

  • timewithoffset

  • timewithoutoffset

  • Default Value: datetimewithoffset

Ability to Define Export Record Limit

PRJCT-10401 | Configurable: Yes

With this release, you can define a limit on the number of records that can be exported using Minerva Export. This controls the file size and performance during export operations.

  • When a limit is configured, the application displays a message next to the Export option. For example, Note: Only the first 5000 records will be exported. This message updates dynamically whenever the configuration value is changed.

  • If no limit is set, exports continue without restriction, and no message is displayed.

Configuration Details:

  • Setting Name: Contracts Minerva Export Record Limit

  • Possible Values: Any numeric whole number values.

  • Default Value: Null

 

Enhanced Contract Mandatory Field Error Validation

PRJCT-10318 | Configurable: Yes

With this release, the Contract creation and saving process is enhanced with a guided validation flow for mandatory fields. When you Save a Contract with missing mandatory details, the application will:

  • Prevent the Contract from being saved and display an error pop-up.

  • Scroll to the first missing field and highlight it in red.

  • Display a static error bar at the top of the screen, displaying the total number of errors and providing Prev / Next arrows for quick navigation.

  • Provides a drop-down error list that allows you to jump directly to specific error fields.

  • Error messages is differentiated between:

  • Standard fields: clear message with field name (e.g., “Please provide contract sub-type”)

  • Custom fields: generic message (e.g., “Please provide missing details”)

  • All missing fields are clearly outlined in red, consistent with the existing UI pattern.

  • This validation is applicable for the following Contract creation flows:

  • Using Contract Template

  • Using Blank Form

  • Store Executed Contract (via Examiner)

  • Flip to Contract

  • Using Contract Request (Request Owner)

  • Using Store Executed Contract

  • RFx to Contract

  • Project to Contract

Configuration Details:

  • Setting Name: Configure Contract Mandatory field error validation

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

Date & Time Display in Recipient Locale for Approval Notifications

PRJCT-10366 | Configurable: Yes

With this release, the date and time attributes in the approval notification table in approval email notifications are displayed according to the recipient’s locale.

  • All date/time attributes in the approval notification table follows the recipient’s locale formatting.

  • In approval email notifications, the Action Taken On column displays the correct offset values as per configuration.

  • This enhancement is applicable for Contract and Contract Request notifications.

Configuration Details:

  • Setting Name: Configure Contract Notification Date & Time Based on Recipient’s Locale

  • Feature Group: CLM.Notification

  • Possible Values: True/False

  • Required Value: True

  • Default Value: False

 

Configuration Details:

  • Setting Name: Configure Contract Date & Time Based on Offset Setting

  • Feature Group: CLM.Notification

  • Possible Values:

  • datewithoffset

  • datewithoutoffset

  • datetimewithoffset

  • datetimewithoutoffset

  • timewithoffset

  • timewithoutoffset

  • Default Value: datetimewithoffset